Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make GCS_MAVLink base class handle DO_SET_HOME #26683

Merged
merged 9 commits into from
Apr 8, 2024

Conversation

peterbarker
Copy link
Contributor

This takes advantage of all our vehicles inheriting from AP_Vehicle, which they didn't when the pure-virtual methods on GCS_MAVLink were first created.

I'm not sure this is the correct shape for handling home generally, but given all but one of our vehicles had the relevant methods already on the vehicle class it seems a reasonable improvement.

There's the basic question of whether home is an AHRS thing or an AP_Vehicle thing. While AHRS has been a good place for home, notionally you don't need AHRS to have a home (Tracker kinda-sorta shows that....)

A first step in further unifying home-position behaviour across vehicle types, anyway.

@peterbarker peterbarker force-pushed the pr/gcs-mavlink-set-home-up branch 6 times, most recently from 2c003cc to 260bd9e Compare April 3, 2024 22:08
@peterbarker peterbarker force-pushed the pr/gcs-mavlink-set-home-up branch from 260bd9e to a736dcb Compare April 4, 2024 23:36
@peterbarker
Copy link
Contributor Author

I've tested this in SITL with Plane, everything works as expected.

@tridge tridge merged commit 44891ce into ArduPilot:master Apr 8, 2024
91 checks passed
@peterbarker peterbarker deleted the pr/gcs-mavlink-set-home-up branch April 9, 2024 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants